Functional versus Non-Functional RequirementsOne of the fundamental objectives of any project is to collect both the functional and non-functional requirements. These need to be kept in balance and harmony, and most importantly not compromised as the project progresses Functional RequirementsThe official definition for a functional requirement specifies what the system should do: "A requirement specifies a function that a system or component must be able to perform." Functional requirements specify specific behavior or functions example of functional requirements: 1-"Display the heart rate, blood pressure and temperature of a patient connected to the patient monitor." Examples of Functional Requirements Functional requirements should include functions performed by specific screens, outlines of work-flows performed by the system, and other business or compliance requirements the system must meet. 1-Interface requirements
Field 1 accepts numeric data entry.
Field 2 only accepts dates before the current date.
Screen 1 can print on-screen data to the printer.
2-Business Requirements
Data must be entered before a request can be approved.
Clicking the Approve button moves the request to the Approval Workflow.
All personnel using the system will be trained according to internal SOP AA-101.
3-Regulatory/Compliance Requirements
The database will have a functional audit trail.
The system will limit access to authorized users.
The spreadsheet can secure data with electronic signatures.
4-Security Requirements
Members of the Data Entry group can enter requests but can not approve or delete requests.
Members of the Managers group can enter or approve a request but can not delete requests.
Members of the Administrators group cannot enter or approve requests but can delete requests.
Depending on the system being described, different categories of requirements are appropriate. System Owners, Key End-Users, Developers, Engineers, and Quality Assurance should all participate in the requirement gathering process, as appropriate to the system.Requirements outlined in the Functional Requirements Specification are usually tested in the Operational Qualification. Non-Functional RequirementsThe official definition for a non-functional requirement specifies how the system should behave: "A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior." Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors, example of nonfunctional requirement: a-"Display of the patient's vital signs must respond to a change in the patient's status within 2 seconds." b-A system may be required to present the user with a display of the number of records in a database. This is a functional requirement. How up-to-date this number needs to be is a non-functional requirement. If the number needs to be updated in real time, the system architects must ensure that the system is capable of updating the displayed record count within an acceptably short interval of the number of records changing
Summary There are two main types of Business Requirements. Functional and Non-Functional Requirements. Functional Requirements are functions and Non-Functional Requirements are considered constraints. Both have the same general characteristics.
Functional
Nonfunctional
Product features
Product properties
Describe the work that is done
Describe the character of the work
Describe the actions with which the work is concerned
Describe the experience of the user while doing the work
Functional versus Non-Functional RequirementsOne of the fundamental objectives of any project is to collect both the functional and non-functional requirements. These need to be kept in balance and harmony, and most importantly not compromised as the project progressesFunctional Requirements The official definition for a functional requirement specifies what the system should do: "A requirement specifies a function that a system or component must be able to perform." Functional requirements specify specific behavior or functions example of functional requirements: 1-"Display the heart rate, blood pressure and temperature of a patient connected to the patient monitor."
Examples of Functional Requirements Functional requirements should include functions performed by specific screens, outlines of work-flows performed by the system, and other business or compliance requirements the system must meet.
1-Interface requirements
- Field 1 accepts numeric data entry.
- Field 2 only accepts dates before the current date.
- Screen 1 can print on-screen data to the printer.
2-Business Requirements- Data must be entered before a request can be approved.
- Clicking the Approve button moves the request to the Approval Workflow.
- All personnel using the system will be trained according to internal SOP AA-101.
3-Regulatory/Compliance Requirements- The database will have a functional audit trail.
- The system will limit access to authorized users.
- The spreadsheet can secure data with electronic signatures.
4-Security Requirements- Members of the Data Entry group can enter requests but can not approve or delete requests.
- Members of the Managers group can enter or approve a request but can not delete requests.
- Members of the Administrators group cannot enter or approve requests but can delete requests.
Depending on the system being described, different categories of requirements are appropriate. System Owners, Key End-Users, Developers, Engineers, and Quality Assurance should all participate in the requirement gathering process, as appropriate to the system. Requirements outlined in the Functional Requirements Specification are usually tested in the Operational Qualification.Non-Functional Requirements The official definition for a non-functional requirement specifies how the system should behave: "A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior." Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors, example of nonfunctional requirement: a-"Display of the patient's vital signs must respond to a change in the patient's status within 2 seconds." b-A system may be required to present the user with a display of the number of records in a database. This is a functional requirement. How up-to-date this number needs to be is a non-functional requirement. If the number needs to be updated in real time, the system architects must ensure that the system is capable of updating the displayed record count within an acceptably short interval of the number of records changing
Summary There are two main types of Business Requirements. Functional and Non-Functional Requirements. Functional Requirements are functions and Non-Functional Requirements are considered constraints. Both have the same general characteristics.
=